Skip to content

Automate version changes#36

Open
RobinKnipe wants to merge 2 commits intomasterfrom
automate-version-changes
Open

Automate version changes#36
RobinKnipe wants to merge 2 commits intomasterfrom
automate-version-changes

Conversation

@RobinKnipe
Copy link
Copy Markdown
Contributor

Provides a way to automatically handle all the necessary changes needed to update the version of the API. Simply run one of the following commands (as appropriate):

  • npm version patch
  • npm version minor
  • npm version major
    ...to update the package.json and .drone.yml versions, commit the changes, and create a git tag of the new version.

In the most recent update the `npm` version declared didn't match the `drone` version. Rather than updating the versions manually, this addition ensures calling one of the following, updates everything automatically:
 - `npm version patch` a patch update: `v0.0.0` -> `v0.0.1`
 - `npm version minor` a minor update: `v0.0.1` -> `v0.1.0`
 - `npm version major` a major update: `v0.1.0` -> `v1.0.0`
@daniel-ac-martin
Copy link
Copy Markdown
Contributor

I think that we implement this in the Makefile. I'd like the npm stuff to be strictly concerned with JavaScript. i.e. It shouldn't have any awareness of Drone.

(I don't want to end up repeating https://github.com/UKHomeOffice/lev-web/blob/master/package.json#L6 ! ;-) )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants